Looks good, but why we need this? I think users can find sender id in raw message.

Looks good, but why we need this? I think users can find sender id in raw message.

That's true, however I find it useful to have the sender ID by default. When downloading many messages the raw field adds a lot of noise in my opinion.

But of course it's just a convenience change.

Cause this PR is some kind of convenience/taste changes, I need owner's options.

@iyear what's your idea?

@zebrapurring tg.PeerClass is a Go interface that contains type and id information. However, when it is converted to JSON, the type information is lost. I suggest creating a new model to convert PeerClass into a structured object

Like:

type PeerClass string

type Peer struct {
    Type PeerClass `json:"type"`
    ID int64 `json:"id"`
}

@zebrapurring tg.PeerClass is a Go interface that contains type and id information. However, when it is converted to JSON, the type information is lost. I suggest creating a new model to convert PeerClass into a structured object

Like:

type PeerClass string

type Peer struct {
    Type PeerClass `json:"type"`
    ID int64 `json:"id"`
}

From what I can see the type information is actually included when serializing the field:

{
    "id": 1234,
    "type": "message",
    "file": "file.jpg",
    "sender": {
        "UserID": 123456
    },
    "date": 1764714525,
    "text": "Hello"
},

@iyear @XMLHexagram any chance to merge this?